﻿<!DOCTYPE html>
<html>
<head>
   <title>Blocks Description</title>
   <meta name="generator" content="Help & Manual">
   <meta name="keywords" content="">
   <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
   <link type="text/css" href="default.css" rel="stylesheet">
   <link type="text/css" href="custom.css" rel="stylesheet">
   <script type="text/javascript" src="nsh.js"></script>
   
<!-- non-scrolling headers for CHM and browser-based help, local styles-->
<style TYPE="text/css" media="screen"> 
   <!-- 
   body {    
      margin:0; 
      padding:0; 
      overflow: auto; 
      background: #edede9; 
   } 
   #idheader { 
      width:100%; 
      height:auto; 
      padding: 0; 
      margin: 0;     
} 
    #idheaderbg  {
    background: #E40A00; 
}
#idheadernowrap  {
    white-space:nowrap; 
}
    ul {list-style-type: lower-roman}
   -->
   </style>
   
<style TYPE="text/css" MEDIA="print">
<!--
/* Hide navigation links and add space between header
     and text in the printed version. Not valid for eBooks. */
#idnav { display:none;	 }
.topichead { padding: 5px 5px 20px 5px; }
-->
</style>   
   <script type="text/javascript" src="jquery.js"></script>
   <script type="text/javascript" src="helpman_settings.js"></script>
   <script type="text/javascript" src="helpman_topicinit.js"></script>

   <script type="text/javascript">
     HMSyncTOC("index.html", "drvsim_tut_blocks_description.htm");
   </script>
   <script type="text/javascript" src="highlight.js"></script>
   <script type="text/javascript">
     $(document).ready(function(){highlight();});
   </script>
</head>
<body>

<!--ZOOMSTOP-->

<div id="idheader" >
<div id="idheaderbg">
<table width="100%" border="0" cellspacing="0" cellpadding="0" 
       style="margin: 0px; color: #D7D7D7;">

  <tr valign="middle">
    <td align="left" valign="middle" class="topichead">
    <!--<div id="idheadernowrap">-->
    <p class="crumbs" id="idnav"><b>Navigation:</b>&nbsp;
   
   VI-DriveSim 19.2 on Linux &gt; <a href="drivesim_tut_tutorials.htm">VI-DriveSim 19.2 Tutorials</a> &gt; <a href="drvsim_tut_external_vehicle_model_using_s.htm">External vehicle model using Simulink</a>&nbsp;&gt;</p>
      <h1 class="p_Heading1" style="page-break-after: avoid;"><span class="f_Heading1">Blocks Description</span></h1>

    <!--</div>-->
    </td>
    <td align="right" width="180" valign="middle" class="topichead" id="idnav">
    <div id="idheadernowrap">
    <a href="javascript: print();"
    		onmouseover="document.images.prntr.src='print_a.png'" 
        onmouseout="document.images.prntr.src='print_n.png'"
        ><img name="prntr" border="0" alt="Print this Topic" title="Print this Topic" src="print_n.png"
        ></a>&nbsp;&nbsp;
     <a href="drvsim_tut_working_principle.htm"
        onmouseover="document.images.prev.src='back_a.png'" 
        onmouseout="document.images.prev.src='back_n.png'"
        ><img name=prev src="back_n.png" border=0 alt="Previous page"
        ></a><a href="drvsim_tut_external_vehicle_model_using_s.htm"
        onmouseover="document.images.main.src='top_a.png'" 
        onmouseout="document.images.main.src='top_n.png'"><img name=main src="top_n.png" border=0 alt="Return to chapter overview"
        ></a><a href="drvsim_tut_hardware-map-template-and-inpu.htm"
        onmouseover="document.images.next.src='next_a.png'" 
        onmouseout="document.images.next.src='next_n.png'"><img name=next src="next_n.png" border=0 alt="Next page"
        ></a>
    </div>
    </td>
  </tr>
</table>
</div>

<!-- The following code displays Expand All/Collapse All links  below the header in topics containing toggles -->
  

</div>  



<div id="idcontent"><div id="innerdiv"> 
<!--ZOOMRESTART-->
<p class="p_Normal">The <span style="font-style: italic;">VI_DriveSim_VehDyn_ext.mdl</span> is a template collecting the blocks available to hook your vehicle model to VI-DriveSim</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal" style="text-align: center;"><img alt="drvsim_tutorial_vehdyn_template" width="890" height="521" style="margin:0px auto 0px auto;width:890px;height:521px;border:none" src="drvsim_tutorial_vehdyn_template.png"/></p>
<p class="p_Normal" style="text-align: center;">&nbsp;</p>
<p class="p_Normal">The green block corresponds to the <span style="font-style: italic;">Interface Input Block</span> while the blue blocks are the <span style="font-style: italic;">Interface Output Blocks</span>. The orange block is an hardware map template which will be detailed explained in the next sections. The input and output ports have the same name of the related value in the Real-Time Database, without the prefix &quot;VI_CarRealTime.Inputs.&quot; and &quot;VI_CarRealTime.Outputs.&quot; for the<span style="font-style: italic;"> Interface Input Blocks</span> and<span style="font-style: italic;"> Interface Output Blocks</span> respectively.</p>
<p class="p_Normal">A complete description of each block is presented below and the list of the input and output signals with their references are reported in the <a href="drvsim_tut_inputs_and_outputs.htm" class="topiclink">Inputs and Outputs</a> section.</p>
<p class="p_Normal">&nbsp;</p>
<p style="text-align: justify; text-indent: 0px; padding: 0px 0px 0px 13px; margin: 0px 0px 0px 0px;"><span style="font-size:10pt; font-family: 'Arial Unicode MS','Lucida Sans Unicode','Arial';color:#000000;display:inline-block;width:13px;margin-left:-13px">&#8226;</span><span style="font-weight: bold;">Cockpit Inputs: </span>the usage of this block is described in the <a href="drvsim_tut_hardware-map-template-and-inpu.htm" class="topiclink">Hardware Map Template and Inputs Manager</a><span style="font-weight: bold;"> </span>section;</p><p class="p_Normal">&nbsp;</p>
<p style="text-align: justify; text-indent: 0px; padding: 0px 0px 0px 13px; margin: 0px 0px 0px 0px;"><span style="font-size:10pt; font-family: 'Arial Unicode MS','Lucida Sans Unicode','Arial';color:#000000;display:inline-block;width:13px;margin-left:-13px">&#8226;</span><span style="font-weight: bold;">iodb_udp: </span>this <span style="font-style: italic;">Interface Output Block</span> sets all the signals required by the VI-DriveSim <span style="font-weight: bold;">iodb_udp.exe</span> module, so it must be placed in the Simulink model if the Simulation Workbench's test will contain it and the<span style="font-style: italic;"> External Vehicle Model</span> created must provide all the input signals of the block;</p><p class="p_Normal">&nbsp;</p>
<p style="text-align: justify; text-indent: 0px; padding: 0px 0px 0px 13px; margin: 0px 0px 0px 0px;"><span style="font-size:10pt; font-family: 'Arial Unicode MS','Lucida Sans Unicode','Arial';color:#000000;display:inline-block;width:13px;margin-left:-13px">&#8226;</span><span style="font-weight: bold;">Steering Wheel: </span>this <span style="font-style: italic;">Interface Input Block</span> represents the interface to the steering wheel system, in particular to the torque value applied to the motor. The External Vehicle Model must provide the Steering Wheel Torque value and this signal is internally multiplied by the TORQUE_MULT, settable from the VI-DriveSim user interface in the<span style="font-style: italic;"> Initial Values</span>. The Simulation Workbench test must contain the<span style="font-weight: bold;"> iodb_elab</span> module in order to use this Simulink block;</p><p class="p_Normal">&nbsp;</p>
<p style="text-align: justify; text-indent: 0px; padding: 0px 0px 0px 13px; margin: 0px 0px 0px 0px;"><span style="font-size:10pt; font-family: 'Arial Unicode MS','Lucida Sans Unicode','Arial';color:#000000;display:inline-block;width:13px;margin-left:-13px">&#8226;</span><span style="font-weight: bold;">Auxiliary Signals: </span>this block is an <span style="font-style: italic;">Interface Output Block </span>and it sets all the auxiliary signals in the RTDB used during the simulation, for example the flag which corresponds to the state of the solver, stored as <span style="font-style: italic;">VI_DriveSim.Outputs.Vicrt.Status </span>in the RTDB. The accepted values for this flag are reported in the <a href="drvsim_tut_inputs_and_outputs.htm" class="topiclink">Inputs and Outputs</a> section;</p><p class="p_Normal">&nbsp;</p>
<p style="text-align: justify; text-indent: 0px; padding: 0px 0px 0px 13px; margin: 0px 0px 0px 0px;"><span style="font-size:10pt; font-family: 'Arial Unicode MS','Lucida Sans Unicode','Arial';color:#000000;display:inline-block;width:13px;margin-left:-13px">&#8226;</span><span style="font-weight: bold;">iodb_cueing:</span> this<span style="font-style: italic;"> Interface Output Block</span> sets all the signals required by the VI-DriveSim <span style="font-weight: bold;">iodb_cueing.exe</span> module. This block is required only when a motion platform is uded.</p><p class="p_Normal">&nbsp;</p>
<p style="text-align: justify; text-indent: 0px; padding: 0px 0px 0px 13px; margin: 0px 0px 0px 0px;"><span style="font-size:10pt; font-family: 'Arial Unicode MS','Lucida Sans Unicode','Arial';color:#000000;display:inline-block;width:13px;margin-left:-13px">&#8226;</span><span style="font-weight: bold;">Active Components: </span>this <span style="font-style: italic;">Interface Output Block</span> is the interface to the VI-grade Active Components, that is the Active Belts and the Active Seat. This block must be added in the Simulink model only if the driving simulator has these technologies. The Simulation Workbench test must include the <span style="font-weight: bold;">iodb_elab.exe</span> process.</p><p class="p_Normal">&nbsp;</p>
<p style="text-align: justify; text-indent: 0px; padding: 0px 0px 0px 13px; margin: 0px 0px 0px 0px;"><span style="font-size:10pt; font-family: 'Arial Unicode MS','Lucida Sans Unicode','Arial';color:#000000;display:inline-block;width:13px;margin-left:-13px">&#8226;</span><span style="font-weight: bold;">iodb_scnr: </span>this <span style="font-style: italic;">Interface Output Block</span> sets all the signals required by the VI-DriveSim <span style="font-weight: bold;">iodb_scnr.exe</span> module, so the it must be placed in the Simulink model if the Simulation Workbench's test will contain it. Please refer to the <a href="drvsim_tut_running_scaner_studio_with_vi-.htm" class="topiclink">Running SCANeR studio with VI-DriveSim</a> tutorial in order to set up the simulation;</p><p class="p_Normal">&nbsp;</p>
<p style="text-align: justify; text-indent: 0px; padding: 0px 0px 0px 13px; margin: 0px 0px 0px 0px;"><span style="font-size:10pt; font-family: 'Arial Unicode MS','Lucida Sans Unicode','Arial';color:#000000;display:inline-block;width:13px;margin-left:-13px">&#8226;</span><span style="font-weight: bold;">Custom Hardware Map Template: </span>this block is an alternative to the cockpit inputs one. the usage of this block is described in the <a href="drvsim_tut_hardware-map-template-and-inpu.htm" class="topiclink">Hardware Map Template and Inputs Manager</a><span style="font-weight: bold;"> </span>section;</p>
<!--ZOOMSTOP-->
</div></div>
<script type="text/javascript"> 
<!-- 
var lastSlashPos = document.URL.lastIndexOf("/") >
document.URL.lastIndexOf("\\") ? document.URL.lastIndexOf("/") :
document.URL.lastIndexOf("\\");
if( document.URL.substring( lastSlashPos + 1, lastSlashPos + 4
).toLowerCase() != "~hh" )
{
    nsrInit();
}
--> 
</script> 
</body>
</html>
